This seems to be more of a problem with 433k than 432. Although I am running 433k now, I recall that it did not have this problem in 432.
For example, if a hardware error is detected (missing index pulse) my axis reffing routine can prompt the user to retry/cancel, and I tested this under 432, and it worked. Just now I was experimenting with the cabling and lost the index pulse: under 433k it just locked the app. Several other cases can also result in user prompts, but I really don't want to have to run all these things using MDI or g-code. And I don't really like the idea of just failing and leaving the axes disabled, and requiring some arcane action on the part of the operator, say to retrieve the last error code.
So, I would respectfully request that you take a look and see if this is something that regressed since 432. The reason I am using 433k is because you mentioned that it fixed a tool table index issue, and I was working on tool change at the time.